Nevron Open Vision Documentation
Framework / Framework Overview
In This Topic
    Framework Overview
    In This Topic

    Nevron Open Vision (NOV) implements the solid foundations that are needed to develop portable presentation layer components. Inside the Framework folder of this documentation you will find the topics that are related to NOV general development. Many of the features and services documented in this folder are often used by other component libraries based on NOV. Following is a brief overview of the Framework modules:

    Data - implementation of data tables and data access to various data sources.

    Data Structures - implementation of commonly used data structures, such as list, stack, queue, map etc. 

    DOM - implementation of W3C-like Document Object Model with integrated support for Cascade Style Sheets and many other enhancements, such as built-in history, expressions etc.

    Graphics - implementation of many graphics related algorithms and painting fundamentals.

    Layouts - implementation of different algorithms for arrangements of boxes, graphs and trees.

    IO (File Systems) - implementation of files and folders that are backed by the local, in-memory and remote file systems.

    Serialization - implementation of a flexible serialization engine, that is capable of serializing both DOM and pure .NET objects.

    Compression - implementation of common algorithms for compression and decompression of data.

    Formulas - implementation of a flexible formula engine that is internally used in DOM expressions, but can be used as a standalone library too.

    Networking - implementation of URI and certain web protocols.

    Resources - implementation of embedded resources that is cross-platform.

    Localization - fundamental support for building localizable applications.

    Although some of the features implemented by the NOV framework modules may be present in the specific environment in which you integrate NOV, it is always preferable to use the NOV implementation over the .NET one, because this will guarantee you almost 100% identical results on all integration environments, not just the one that you currently target.